Dedicated Or Integrated Adapter Card

ABSTRACT

An adapter card including a processing unit, an assigned memory and a system bus interface are disclosed. The system bus interface is connectable to at least one system bus of a primary computer system providing a connection to a number of at least one central processing units of the primary computer system, the number of at least one central processing units providing a plurality of processing entities. Configuration data stored in the assigned memory includes data defining all processing entities of all central processing units of the central computer system. The adapter card is operative to perform computations including: obtaining a system object representing a callable unit of a program from a program environment, transforming the system object into a plurality of threads, each thread being executable by one processing entity, assigning each thread to one processing entity, and transmitting each thread to the assigned processing entity for execution.

TECHNICAL FIELD

The present teachings relate generally to parallel computing, and moreparticularly to adapter cards (e.g., dedicated, integrated, etc.) forforming computer grid structures.

BACKGROUND

To increase the hardware power, modern computers utilize a plurality ofparallel CPUs (Multi-CPU), usually having multiple cores (Multi-CORE)which can be adapted to handle a plurality of parallel threads ofexecution in one core (Multi-Hardware-Threads). To increase thecalculation power even more, a plurality of computers can be connectedover local or wide area networks to form a grid to enable highperformance computing. Complex computational tasks can be calculated ina parallel manner on a plurality of computers connected in a grid.

To deploy the full hardware power of such computer systems and gridscomputer programs have to be “tailored” for specific computer or gridarchitecture. There are several tools and methods for implementing aparallel execution, which are defined in parallel execution models, e.g.POSIX threads, JAVA threads, more object oriented methods like boostlibrary, which are difficult to handle also for a talented andexperienced programmer. Other approaches that could be easier to handle,like JAVA and .NET solutions, are actually unacceptable for most highperformance computing tasks, as they are by default to slow.

Therefore many problems arise from parallel computing in real worldprogramming, e.g. that a diligently designed software is not runningwith the right performance or that a program is not scalable over nodesin a grid, CPUs in a node, or Cores in a CPU. Software systems forparallel execution often have a high defect rate, are hard to reuse ordebug, etc.

SUMMARY

The needs set forth herein as well as further and other needs andadvantages are addressed by the present embodiments, which illustratesolutions and advantages described below.

Current solutions are working with direct usage of parallelizationtechnologies, like threads, processes, semaphore, shared memory, mutex,OpenMPI, OpenMP, etc., by using different system implementationsmentioned above. This approach usually creates an unreliable code, whichhas a high defect rate, stays below the expectations of performance, andleads mostly to an unreadable code, which is hard to attain or toextend.

It is a goal of the present teachings to provide apparatus and methodsto improve parallel computing solutions and in particular to reduce thedefect rate and increase the scalability and portability of programsrunning on parallel computer systems.

In a first aspect, these goals are achieve by an adapter card having aprocessing unit, an assigned memory, and a system bus interface. Thesystem bus interface is connectable to at least one system bus of aprimary computer system providing a connection to a number of at leastone central processing units of the primary computer system, the numberof at least one central processing units providing a plurality ofprocessing entities. Configuration data stored in the assigned memorycomprises data defining all processing entities of all centralprocessing units of the primary computer system. The adapter card isoperative to perform computations comprising the following:

-   -   obtaining a system object representing a callable unit of a        program from a program environment,    -   transforming the system object into a plurality of threads, each        thread being executable by one processing entity,    -   assigning each thread to one processing entity,    -   transmitting each thread to the assigned processing entity for        execution,    -   receiving computation results from each processing entity,    -   determining an outcome of the system object based on the        computation results,    -   returning the outcome to the program environment.

Other embodiments of the system and method are described in detail belowand are also part of the present teachings.

BRIEF DESCRIPTION OF THE DRAWINGS

The present teachings will further be described in terms ofnon-restricting examples of preferred embodiments, which are given inconnection with the accompanying drawings, wherein

FIG. 1 depicts an adapter card according to the present teachings in aschematic representation,

FIG. 2 shows a schematic overview over a grid-computing infrastructure,

FIG. 3 shows a schematic block diagram illustrating the structure andexecution of a software program.

DETAILED DESCRIPTION

The present teachings are described more fully hereinafter withreference to the accompanying drawings, in which the present embodimentsare shown. The following description is presented for illustrativepurposes only and the present teachings should not be limited to theseembodiments. Any computer configuration and architecture satisfying thespeed and interface requirements herein described may be suitable forimplementing the system and method of the present embodiments.

In compliance with the statute, the present teachings have beendescribed in language more or less specific as to structural andmethodical features. It is to be understood, however, that the presentteachings are not limited to the specific features shown and described,since the systems and methods herein disclosed comprise preferred formsof putting the present teachings into effect.

For purposes of explanation and not limitation, specific details are setforth such as particular architectures, interfaces, techniques, etc., inorder to provide a thorough understanding. In other instances, detaileddescriptions of well-known devices, circuits, and methods are omitted soas not to obscure the description with unnecessary detail.

Generally, all terms used in the claims are to be interpreted accordingto their ordinary meaning in the technical field, unless explicitlydefined otherwise herein. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methoddisclosed herein do not have to be performed in the exact orderdisclosed, unless explicitly stated. The use of “first”, “second,” etc.for different features/components of the present disclosure are onlyintended to distinguish the features/components from other similarfeatures/components and not to impart any order or hierarchy to thefeatures/components.

FIG. 1 shows an inventive adapter card 1 comprising a processing unit 2,an assigned memory 3, a network interface 5, and a system bus interface4.

The adapter card 1 can be implemented as a dedicated (or discrete)adapter card 1, which is a physical hardware unit e.g. in form of anexpansion card, expansion board or accessory card. The dedicated adaptercard 1 may comprise a printed circuit board that has a system businterface 4 to be inserted into an electrical connector, or expansionslot on a computer motherboard, backplane or riser card to addfunctionality to the computer system. The processing unit 2, the memory3, and the network interface 5 may be provided on the printed circuitboard, e.g. in the form of an electronic circuit and integrated circuitelements. The electrical connectors of the system bus interface 4 canprovide connectivity to the system bus of the computer system eitherdirectly or via a card bus or expansion bus according to well-knownstandards.

The adapter card 1 can also be implemented as an integrated or “virtual”adapter card, i.e. the elements of the adapter card 1 are integratedinto the motherboard of the computer system. In this case the functionof processing unit 2 of the adapter card 1 can be performed by the CPUof the computer system and the dedicated memory 3 can be a part of thecomputer memory. The readily existing connection of the CPU to thesystem bus can be used as the system bus interface 4. As a networkinterface 5 any network interface available on the computer system canbe used. The embodiment as an integrated adapter card 1 allows for asoftware implementation of the inventive adapter card 1 on a variety ofsuitable computer hardware.

The network interface 5 provides a data connection to remote hardwareunits using a suitable network protocol, for example a network protocolof the internet protocol suite, such as TCP/IP or UDP/IP. Nonethelessthe present teachings are not restricted to these protocols and anynetwork protocol known in the art can be used.

FIG. 2 shows an exemplary distributed system or grid computing structure14 that can be used according to the present teachings.

A primary computer system 7 is provided with the (dedicated orintegrated) adapter card 1, which is connected to a system bus 6 of thecomputer system 7 via the system bus interface 4. The primary computersystem 7 has at least one central processing unit (CPU) 8, alsoconnected to the system bus 6 in a known manner. Also at least onecomputer memory 12 is connected to the CPU 8 and the adapter card 1 viathe system bus 6.

The CPU 8 provides a number of processing entities 11 to the operatingsystem of the computer system 7. The term “processing entity” as it isused in the context of this disclosure describes the smallest entity ofa CPU that can independently read and execute program instructions. Eachprocessing entity 11 appears to the operating system as an independentprocessor that can be addressed in a parallel manner.

Each CPU 8 provides at least one processing entity 11, but in thecontext of high performance computing modern computer systems usuallyhave more than one processing entity 11. For example the CPU 8 can be amulticore-processor having a plurality of cores 13. A core is anindependent actual processing unit within the CPU 8 that can read andexecute program instructions independently from other cores of the CPU8. Further each core 13 can allow multi-threading, i.e. one physicalcore appears as multiple processing entities 11 to the operating system,sometimes referred to as “hardware threads”. In other cases each core 13of the CPU 8 can be a single processing entity 11 or the CPU 8 itselfcan be a single processing entity 11.

The primary computer system 7 can additionally have one or moresecondary CPUs 8′, one of which is schematically shown in FIG. 2 indotted lines. The secondary CPU 8′ (and any further secondary CPU, asthe case may be) can essentially have the same features as the first CPU8 and provides one or more processing entities 11′ in one or more cores13′.

The network interface 5 provides a connection to a number of remotecomputer systems 107, 207, 1007 via a network 10. In FIG. 2 a firstremote computer system 107, a second remote computer system 207 and atenth remote computer system 1007 are shown in an exemplary manner andit should be noted that any number of computer systems can be used inconnection with the inventive systems and methods. Each of the remotecomputer systems 101, 201, 1001 comprises one remote adapter card 101,201, 1001, each of them being connected to the network 10 via theirrespective network interfaces 105, 205, 1005. All adaptor cards 1, 101,201, 1001 can send and receive data via the network 10. The remoteadapter cards 101, 201, 1001 can, independently from each other, beimplemented as dedicated or integrated adapter cards.

The remote computer systems 107, 207, 1007 can be identical to ordifferent from the primary computer system 7 and they particularly canhave all features that are described above in connection with thedescription of the primary computer 7, e.g. a computer memory 112, 212,1012, a system bus 106, 206, 1006. Each of the remote computer systems107, 207, 1007 has at least one remote central processing unit 108, 208,1008 providing at least one remote processing entity 111, 211, 1011.Some or all of the remote computer systems 107, 207, 1007 canadditionally have one or more secondary CPUs (similar to the secondaryCPU 8′ of the primary computer system 7), which are not depicted in FIG.2 for reasons of simplicity and clarity.

Returning to the detailed depiction of the adapter card in FIG. 1, theadapter card 1 comprises configuration data 9 which is stored in theassigned memory 3 of the adapter card 1. The configuration data 9 can,for example, be set up in the form of an .ini-file or another suitabledata format.

The configuration data 9 defines the hardware environment of the adaptercard 1, the number and communication addresses of all other remoteadapter cards 101, 201, 1001 that are available in the grid computingstructure 14 (see again FIG. 2) and the hardware environments of allremote computer systems 107, 207, 1007 in this grid computing structure14. Further the configuration data 9 may comprise all necessaryinformation needed by the adapter card 1 to address every singleprocessing entity in the grid computing structure 14, either within theprimary computer system 7 via the system bus 6, or within any otherremote computer system 107, 207, 1007 in the grid via the network 10 andthe respective remote adapter card 101, 201, 1001 which is connected tothe respective system bus 106, 206, 1006 of the respective remotecomputer system 107, 207, 1007 via its own system bus interface.

The description herein describes a primary computer system 7 comprisinga primary adapter card 1 and a plurality of remote computer systems 107,207, 1007 each having a remote adapter card 101, 201, 1001. Nonethelessis obvious to the person skilled in the art that all adapter cards 1,101, 201, 1001 could be essentially identical, so that each of theremote computer systems 107, 207, 1007, for example the second remotecomputer system 202, could be used as a primary computer system, inwhich case all other computer systems 7, 107 and 1007 in the gridcomputing structure 14 would act as a remote computer system. Thedistinction between “primary” and “remote” items is only given forcomprehensibility and clarity of the description and should not beconstrued in a restrictive manner.

The configuration data 9 of an adaptor card 1 can comprise differentdefinitions for a direct hardware environment and a remote hardwareenvironment. The term “direct hardware environment” designates thehardware within the same computer system 7 as the respective adaptorcard 1, in particular the CPUs 8, 8′ and computer memory 12 that isconnected to the adaptor card 1 via the system bus interface 4 of thisadaptor card 1. Conversely, the term “remote hardware environment”designates all hardware entities that can be addressed via the networkinterface 5 and a remote adaptor card 101, 201, 1001, particularly theCPUs 108, 208, 1008 and computer memories of the remote computer systems107, 207, 1007.

An identical set of configuration data 9 can be provided for all adaptorcards in the grid computing structure 14. In a different approachconfiguration data 9 stored in one adaptor card 1 is not identical tothe configuration data 9 that is stored on the other adaptor cards 101,201, 1001 in the grid computing structure 14. Nonetheless theconfiguration data of all remote adapter cards 1, 101, 201, 1001 in thesame grid computing structure 14 may be consistent with each other inthat they describe the same grid computing structure 14, i.e. theconfiguration data 9 provides detailed information of all processingentities 11, 111, 211, 1011 in the grid computing structure 14 to all(primary and remote) adapter cards 1, 101, 201, 1001.

It should be noted that the grid computing structure 14 is not definedby the units of hardware (i.e. computer systems 7, 107, 207, 1007) thatare physically connected in the same network 10. This would obviouslynot be possible, for example in the case where the network 10 is theinternet. Rather the grid computing structure 14 may be defined by oneset of common configuration data 9 that is used by a number of adaptercards 1, 101, 201, 1001. This allows an easy change or modification of agrid computing structure 14. For example a second set of configurationdata 9 could be shared by the primary adapter card 1 and the secondremote adaptor card 201, which would define a grid computing structure14′ that comprises only the primary computer system 7 and the secondremote computer system 207. Once it is defined, a grid computingstructure 14, 14′ can be reused for other software programs. Newdefinitions for a new grid computing structure can be based on anexisting definition as a template.

As will be understood by the following description of preferred methodsof operation that can be implemented with the inventive systems thedefinition of the grid computing structure 14 can be chosenindependently from the software program that is to be executed in aparallel manner by the grid computing structure 14. This allows theprogrammer of the software program to focus his efforts on the abstractparallelization strategies without taking into account existing hardwarerestrictions.

In the following, a general concept of a computer software structureshall be described in a generic manner with reference to FIG. 3.Independent of a specific programming language, any software program canbe seen as a sequence f( . . . ) of program instructions, which can havea very complex structure. The sequence f( . . . ) can be structured intoseparate callable units f_(i)( . . . ) (i=1 . . . n) that perform aspecific task. Callable units are often also referred to as subroutines,procedures, functions, routines, methods, or subprograms. By designingthe structure and parameters of the callable units programmers createthe software program.

Callable units are written according to a programming language. To beexecuted by the hardware of a computer system the callable units firsthave to be translated into a system object O^(fi) containing objectcode, usually in a machine code language. This translation is known ascompiling. Upon execution, this system object O^(fi) is furthertransformed into a number of Threads of execution O_(k) ^(fi) (k=0 . . .m).

The term “thread of execution” (sometimes simply referred to as“thread”), as it is used in the context of this disclosure is defined asthe smallest sequence of programmed instructions that can be managed bya scheduler of an operating system. In the context of the presentdisclosure each thread of execution will be executed by one processingentity 11.

In the context of the concept of computer software shown in FIG. 3,three domains can be established for the design and execution ofcomputer programs: Firstly a software program environment 15, secondly amachine code environment 16 and thirdly a hardware environment 17.

To date for the development of software that is especially suitable forparallel computing, programmers have to take into account not only thesoftware program environment 15, with which they are very familiar, butalso the machine code environment 16 and the hardware on which thesoftware runs, which often poses difficulties also to experiencedprogrammers. The need to take into account the specific machine codeenvironment 16 (and also a specific hardware environment 17) for thecreation of the software (i.e. in the software program environment 15)inevitably results in complicated and bulky code. The effects that achange in the hardware environment 15 has on the performance of thesoftware are often unpredictable so that the software has to be adaptedevery time the hardware environment 17 changes.

The present teachings allow a clear separation of the abstractparallelization of the algorithm and the execution of this software inthe machine code environment 16 and hardware environment 17. Theprogrammer creates the software program by defining and structuring thecallable units. To define the abstract parallelization the programmerfirst analyses the problem domain and decides which callable units haveto be active (autonomously running) and which callable units have to bepassive (only attached to the active objects as e.g. data containers).

The term “abstract parallelization”, as it is used in the context of thepresent disclosure, refers to the analyzation of the parallelization ofan algorithm and the breakdown into a set of sub-algorithms that aredesignated as synchronous or asynchronous parallel algorithms.Particularly this can be done by code generation by defining thesub-algorithms as callable units.

The programmer defines the properties of the active callable units (forexample what does the callable unit execute, which data are needed,etc.). He decides which active callable unit can be split insynchronously running sub processes or asynchronously running subprocesses. He is doing only the abstract process of understanding theparallelization in a meta programming language, which can be close tothe C++ or CORBA idl language. For example code generation can be doneby a code generator, which reads the callable units and creates a readyto compile and link C++ class, which fits into an active system objectadapter of the adapter card. The code generation “envelopes” the activecallable units with the code that is understood by the adapter card.

Upon execution of the software program, the sequence f( . . . ) ofcallable units f_(i)( . . . ) gets translated into a set of systemobjects O^(fi), that are defined in a form that can be processed by theadapter card 1.

The system objects O^(fi) include all definitions of the abstractparallelization so that the adapter card 1 is able to understand therestrictions and mutual dependencies of the system objects and theprotected shared data segments that are necessary for execution of thesystem objects.

Based on this information the adapter card 1 transforms the systemobjects O^(fi) into a number of threads of execution O_(k) ^(fi). Forexample the threads of execution can be defined according to OpenMPImethods or as POSIX/Windows Threads. In other words, the componenttranslates the information for the operating system and hardware systemfor execution. The transformation into threads of execution is done byalgorithms that rely on the definitions of the abstract parallelization,i.e. for this step the adapter card 1 may not take into account thehardware resources that are available in the grid computing structure14, but relies on the abstract parallelization defined by theprogrammer.

In the next step, which is the execution of the threads on a CPU, theactual available hardware resources have to be taken into account.According to the configuration data 9 the adapter card 1 receives statusmessages 18 from all remote adapter cards 101, 201, 1001 and sendsrespective status messages 18 to all the remote adapter cards 101, 201,1001 in the grid computing structure 14. These status messages 18contain data about the current work load and memory usage of therespective (primary or remote) computer system 7, 107, 207, 1007. Thestatus messages 18 are preferably sent according to a regular scheme sothat every adapter card 1, 101, 201, 1001 can maintain a currentworkload table in which workload and memory usage data of all computersystems in the grid computing structure 14 are recorded. Further“historic” data of the workload and memory usage can be stored in thesame way, to provide an overview of the recent development of workloadand memory usage in each computer system. The required length of thetime period that historic data are preserved may depend on theprediction algorithms that are being used by the adapter card 1 topredict the future workload and memory usage which are described below.Usually a time period of some milliseconds time, e.g. less than 10 msinto the past, can be adequate to obtain satisfactory predictionresults.

It is desirable to keep the actuality of the workload and memory usagedata as close to real time as possible, especially by reducing any lagsthat can occur in the communication over the network 10. With a properhardware infrastructure the current workload table can be maintainedalmost in real time. The maximum time lags of the system can beminimized by optimizing the hardware and the operation system.

Having structured the threads of execution and their interdependencies,the adapter card 1 may now predict the resources that will be necessaryfor the execution of each thread. Further the adapter card 1 may use aprediction algorithm to calculate a predicted workload of the processingentities 11, 111, 211, 1011 in the grid computing structure 14 and therespective memory usages of these processing entities for the nearfuture. This allows for a prediction of the free capacities theprocessing entities will probably have. Known heuristic or deterministicprediction algorithms can be used for this prediction.

The adapter card now can map the necessary resources for execution ofeach thread to the predicted capacities of the processing entities. Thismapping can be done by known algorithms, e.g. randomized algorithms thatmap the threads at least partly according to a random distribution,round-robin-algorithms that assign the threads according to a givenorder, etc.

According to this mapping the adapter card 1 assigns each thread O_(k)^(fi) to one processing entity 11 in the grid computing structure 14 andtransmits the threads O_(k) ^(fi) to the assigned processing entity 11for execution. The processing entities 11 compute results and transmitthe computed results back to the adapter card 1.

The adapter card 1 can either address a processing entity 11 within theprimary computer system 7 directly via the system bus 6, or it canaddress a processing entity 111, 211, 1011 in one of the remote computersystems 107, 207, 1007 by transmitting the thread of execution to theremote adapter card 101, 201, 1001 in this computer system, although notlimited thereto. The adapter card 1 can either transmit single threadsof execution to the remote adapter cards, or it can transmit systemobjects that shall be executed by the respective remote computer systemunder the control of the respective remote adapter card, although notlimited thereto.

The process of prediction of free resources and mapping of threadsaccording to these predictions can be done in a highly dynamic manner,so that the adapter card 1 can react to changes of the workload thatoccur in one, more or all computer systems in real time, even while theexecution of a program is already running.

The adapter card 1 distributes the system objects to and receivescomputation results from the processing entities 11. Further the adaptercard 1 keeps track of all system objects and threads of execution in theway of a core process which keeps an overview over the distributedtasks.

According to the differently parallelized tasks of execution and thecore process the adapter card 1 assembles the input and output data fromthe system objects and tasks and, where appropriate, assembles them withfurther tasks of execution from other system objects that are executedin a parallel manner.

In this way the system objects (or threads of execution, respectively)are executed on the assigned processing entities 11 and their executionis controlled by the core process running on the adapter card 1 throughsending control signals. The techniques that can be used for theexecution and organization of the parallel execution of threads and/orsystem objects are known per se in the state of the art. With knowledgeof the teachings of this disclosure, the person skilled in the art isable to select and implement respective schemes and techniques.

The outcome of the execution is then returned to the program environment15.

The definition of a grid computing structure 14, 14′ can be created bythe programmer independently from the software program to be executed.To “build” a grid computing structure 14, the adapter card 1 can forexample read in a file containing the definition data 9 and send thedefinition data 9 to all remote adapter cards 101, 201, 1001 in the gridcomputing structure 14 that should be built up.

The creation of the grid computing structure 14 can also be defined inform of a configuration script within the software program that assignsparameters (like CPU, CORE or hardware thread ID or network address andport) and can be read by the adapter card 1 at the execution of theprogram. Although the configuration script is a part of the softwareprogram, it is to be noted that this definition is still independentfrom the abstract parallelization and can easily be changed withoutchanging the abstract parallelization.

The use of configuration scripts could also allow for a use of differentdefinitions of grid computing structures 14, 14′ within one singlesoftware program, e.g. by defining different groups of callable unitsthat can be performed in parallel, each group being allocated to adifferent grid computing structure 14, 14′. For the execution of theprogram the adapter card 1 can maintain two or more different gridcomputing structures 14, 14′ while executing one software program.

While the present teachings have been described above in terms ofspecific embodiments, it is to be understood that they are not limitedto these disclosed embodiments. Many modifications and other embodimentswill come to mind to those skilled in the art to which this pertains,and which are intended to be and are covered by both this disclosure andthe appended claims. It is intended that the scope of the presentteachings should be determined by proper interpretation and constructionof the appended claims and their legal equivalents, as understood bythose of skill in the art relying upon the disclosure in thisspecification and the attached drawings.

LIST OF REFERENCES

-   adapter card 1-   processing unit 2-   assigned memory 3-   system bus interface 4-   network interface 5-   system bus 6-   primary computer system 7-   central processing unit 8-   configuration data 9-   network 10-   processing entity 11-   computer memory 12-   cores 13-   grid computing structure 14-   software program environment 15-   machine code environment 16-   hardware environment 17-   status messages 18-   program (f)-   callable unit (f_(i))-   system object (O^(fi))-   thread (O_(k) ^(fi))

What is claimed is:
 1. An adapter card comprising a processing unit, anassigned memory, and a system bus interface, wherein the system businterface is connectable to at least one system bus of a primarycomputer system providing a connection to a number of at least onecentral processing units of the primary computer system, the number ofat least one central processing units providing a plurality ofprocessing entities, configuration data stored in the assigned memorycomprises data defining all processing entities of all centralprocessing units of the primary computer system, the adapter card beingoperative to perform computations comprising the following: obtaining asystem object representing a callable unit of a program from a programenvironment, transforming the system object into a plurality of threads,each thread being executable by one processing entity, assigning eachthread to one processing entity, transmitting each thread to theassigned processing entity for execution, receiving computation resultsfrom each processing entity, determining an outcome of the system objectbased on the computation results, returning the outcome to the programenvironment.
 2. The adapter card according to claim 1, wherein thesystem object comprises at least one parallelization definition and thetransforming the system object into a plurality of threads is based atleast in part on the parallelization definition.
 3. The adapter cardaccording to claim 1, wherein the assigning each thread to oneprocessing entity is performed taking into account the configurationdata.
 4. The adapter card according to claim 1, wherein the adapter cardis operative to receive current workload data representing a currentworkload of each processing entity and wherein the assigning each threadto one processing entity takes into account the current workload data.5. The adapter card according to claim 1, wherein the assigning eachthread to one processing entity, transmitting each thread to theassigned processing entity for execution, receiving computation resultsfrom each processing entity, and determining an outcome of the systemobject based on the computation results comprise controlling data accessto shared memory according to a parallel execution model.
 6. An adaptercard comprising a processing unit an assigned memory, a networkinterface, and a system bus interface, wherein the system bus interfaceis connectable to at least one system bus of a primary computer systemproviding a connection to a number of at least one central processingunits of the primary computer system, the number of at least one centralprocessing units providing a plurality of processing entities, thenetwork interface is adapted to provide a communication via a network toat least one of a number of remote adapter cards, each remote adaptercard being connected to a system bus of a remote computer system havingat least one remote central processing unit having at least one remoteprocessing entity, configuration data stored in the assigned memorycomprises data defining all processing entities of all centralprocessing units of the primary computer system, the configuration data)further comprises data defining all processing entities of all remotecentral processing units of all remote computer systems, the adaptercard being operative to perform computations comprising the following:obtaining a system object representing a callable unit of a program froma program environment, transforming the system object into a pluralityof threads, each thread being executable by one processing entity,assigning each thread to one processing entity, transmitting each threadto the assigned processing entity for execution, receiving computationresults from each processing entity, determining an outcome of thesystem object based on the computation results, returning the outcome tothe program environment.
 7. The adapter card according to claim 6,wherein the adapter card is operative to receive from at least one firstremote adapter card status messages comprising current workload datathat represent a current workload of the processing entities in therespective remote computer system.
 8. The adapter card according toclaim 6, wherein the adapter card is operative to send to at least onefirst remote adapter card status messages comprising current workloaddata representing a current workload of the processing entities of theprimary computer system.
 9. A method for executing a program that isdefined as a structured plurality of callable units, the methodperformed by an adapter card having a processing unit, an assignedmemory, a network interface, and a system bus interface, the adaptercard having software executing on computer readable media to perform thefollowing: obtaining a system object representing a callable unit of aprogram from a program environment, transforming the system object intoa plurality of threads, each thread being executable by one processingentity, assigning each thread to one processing entity, transmittingeach thread to the assigned processing entity for execution, receivingcomputation results from each processing entity, determining an outcomeof the system object based on the computation results, returning theoutcome to the program environment.
 10. The method according to claim 9,wherein the system object comprises at least one parallelizationdefinition and the transforming the system object into a plurality ofthreads is based at least in part on the parallelization definition. 11.The method according to claim 9, wherein the assigning each thread toone processing entity is performed taking into account configurationdata stored in the assigned memory of the adapter card.
 12. The methodaccording to claim 9, wherein the adapter card receives current workloaddata representing the current workload of each processing entity andwherein the assigning each thread to one processing entity takes intoaccount the current workload of each processing entity.
 13. The methodaccording to claim 9, wherein the assigning each thread to oneprocessing entity, transmitting each thread to the assigned processingentity for execution, receiving computation results from each processingentity, and determining an outcome of the system object based on thecomputation results comprise controlling data access to shared memoryaccording to a parallel execution model.
 14. The method according toclaim 9, wherein the adapter card receives from at least one firstremote adapter card status messages comprising current workload datathat represent a current workload of processing entities in a respectiveremote computer system.
 15. A grid computing structure comprising aprimary computer system and a number of at least one remote computersystems, the primary computer system and each remote computer systemcomprise an adapter card according to claim 6, wherein the networkinterfaces of the respective adapter cards are adapted communicate toother adapter cards via a network.